crypto: asymmetric_keys - handle EBUSY due to backlog correctly
authorGilad Ben-Yossef <gilad@benyossef.com>
Thu, 18 May 2017 13:29:23 +0000 (16:29 +0300)
committerRaspbian kernel package updater <root@raspbian.org>
Sun, 23 Jul 2017 02:54:40 +0000 (02:54 +0000)
commit96823d1efe1f8b96980b511db110814161be3e52
tree8fe1d6e7e23834341fee32f8421a32a06f3470f6
parent308d68a01d21efc13ac4bde54e56d3ecc131f08c
crypto: asymmetric_keys - handle EBUSY due to backlog correctly

commit e68368aed56324e2e38d4f6b044bb8cf82077fc2 upstream.

public_key_verify_signature() was passing the CRYPTO_TFM_REQ_MAY_BACKLOG
flag to akcipher_request_set_callback() but was not handling correctly
the case where a -EBUSY error could be returned from the call to
crypto_akcipher_verify() if backlog was used, possibly casuing
data corruption due to use-after-free of buffers.

Resolve this by handling -EBUSY correctly.

Signed-off-by: Gilad Ben-Yossef <gilad@benyossef.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
crypto/asymmetric_keys/public_key.c